ci: publish the modelparams package to npm#62
Merged
Conversation
The release workflow could never publish: it pushed the version bump to protected main (rejected by branch protection), and CI's npm 10 was too old for the OIDC trusted publisher (ENEEDAUTH). - Tag-only release: publish + tag via the release action, never push to main - Version derived from the latest modelparams@x.y.z tag; first release seeds from package.json - CI runs Node 24 (npm 11) so OIDC trusted publishing works
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💭 Why
The release workflow could never publish. It pushed the version bump to protected
main(rejected by branch protection), and CI's npm 10 was too old for the OIDC trusted publisher (ENEEDAUTH).✨ What changed
main.modelparams@x.y.ztag; first release seeds frompackage.json.🔧 For operators
On merge, the workflow auto-publishes
modelparams@0.0.1via the trusted publisher. Future catalog changes publish automatically (patch, or major when a param is removed).